Medication safety devices and methods

ABSTRACT

A medication safety device and method can include an infusion pump and a drug library in communication with the infusion pump. The drug library can have upper hard and soft limits and lower hard and soft limits associated with at least one drug. A graphical user interface can display a bar chart showing upper and lower soft limit bars for the at least one drug. The upper and lower soft limit bars can be grabbed and dragged on the graphical user interface in touch-screen fashion to new positions associated with new upper and lower soft limits. The graphical user interface and associated hardware and software can be configurable to responsively re-analyze data and compare a particular infusion to the new upper and lower soft limits.

RELATED APPLICATIONS

This application is a continuation of application Ser. No. 14/763,985 filed Jul. 28, 2015, which is a National Phase entry of PCT Application No. PCT/US2014/012757, filed Jan. 23, 2014, which claims the benefit of U.S. Patent Application No. 61/757,587 entitled “MEDICATION SAFETY DEVICES AND METHODS” and filed Jan. 28, 2013, and U.S. Patent Application No. 61/826,253 entitled “MEDICATION SAFETY DEVICES AND METHODS” and filed May 22, 2013, each of which are incorporated herein by reference in their entireties.

TECHNICAL FIELD

This disclosure relates generally to medical systems, devices, and methods for facilitating the safe delivery of medication. In particular, it relates to systems, devices and methods for the operation of medical infusion pumps, and for the development and maintenance of drug libraries used in the operation of such pumps.

BACKGROUND

Medical infusion pumps are used to infuse liquids, such as nutrients and medicaments, into the circulatory system of a patient. Such pumps provide a wide range of flexibility in administering such fluids. For instance, the rate at which a medicament is introduced into the circulatory system can be variably programmed, the total volume to be administered can be pre-set, and the time for administering the medicament can be scheduled for automatic delivery at a certain periodicity. While the pre-programming of infusion rates, times and amounts with infusion pumps enables a wide variety of treatment protocols that would be impractical, expensive or unreliable if performed manually, it also presents the challenge of safely controlling the introduction of fluids into a patient when medical personnel are not continuously present.

Medical infusion pumps can be classified as large volume or small volume. Large volume pumps are typically used for medications and fluids, such as nutrients, that need to be delivered to patients in relatively large volumes compared to other medications and fluids, while small volume pumps can be used to infuse insulin or other medicines such as opiates. While small volume pumps can take different forms, syringe pumps are one of several types of pumps that can provide precision infusion of small amounts of fluid.

A syringe pump typically employs a pre-filled medication syringe that is mechanically driven under microprocessor control to deliver a prescribed amount or dose of a fluid at a controlled rate to a patient through an infusion line fluidly connected to the syringe. Syringe pumps typically include a motor that rotates a leadscrew. The leadscrew in turn activates a plunger driver which forwardly pushes a plunger within a barrel of the syringe. Pushing the plunger forward thus forces the dose of medication outwardly from the syringe, into the infusion line, and to the patient—typically, intravenously. Examples of syringe pumps are disclosed in U.S. Pat. No. 4,978,335 titled “Infusion Pump with Bar Code Input to Computer”, U.S. Pat. No. 8,182,461 titled “Syringe Pump Rapid Occlusion Detection System”, and U.S. Pat. No. 8,209,060 titled “Updating Syringe Profiles for a Syringe Pump,” each of which is incorporated herein by reference in its entirety. As used throughout this disclosure, the term “syringe pump” is intended to generally pertain to any device which acts on a syringe to controllably force fluid outwardly therefrom.

Syringe pumps are used to control delivery to a patient of medications or fluids that include, but are not limited to: therapeutic agents; nutrients; drugs; medicaments such as antibiotics, blood clotting agents, and analgesics; and other fluids. The devices can be used to introduce the medications or fluids into the body of a patient utilizing any of several routes such as, for example, intravenously, subcutaneously, arterially, or epidurally.

To enhance patient safety during infusions, syringe pump manufacturers have developed so-called “smart” pumps that may provide functionality beyond just the delivery of fluids to a patient by the aforedescribed mechanical means. Smart pumps typically provide information concerning, or might even impose, safety limits on medication program parameters such as dose, concentration, and time, etc., for delivery of a particular medication from the pump to a particular patient. Consequently, more work may be required from practitioners to create and maintain so-called “drug libraries” associated with such safety limits. Provision of such functionality may be considered as being of higher importance in certain practices, protocols, and standardized procedures. There may be not as much emphasis or need for standardization, provision of pump safety limits, or restrictions on medication dosing rate ranges, however, with other practices and protocols. Thus, there is an unmet need for pumps that provide several levels of functionality.

In settings that typically do not require a high degree of functionality with safety limits and/or drug libraries for pumps, practitioners are usually accustomed to workflows that are much simpler than those of smart pumps. A simple workflow is usually defined as “Rate, Volume, Run” or a similar, basic controlled infusion protocol. Conversely, a more fully controlled infusion would typically employ applicable safety limits, which are commonly referred to as “hard” and “soft” limits, on delivery of a particular medication. A hard limit is often defined as a limit for which a selected infusion parameter that is outside of the limit results in generation of an alert and rendering of the pump inoperative or unable to accept selection or input of the parameter. Hard limits are typically set for high-risk drugs such as heparin. A soft limit, however, is often defined as a limit which may generate an alert but still may be overridden so that the infusion may proceed. When hard and/or soft limits are employed with a smart pump, information is usually input to the pump—or another system in communication with or controlling the pump—which includes data such as patient weight, the type of medication being infused, and the prescribed drug concentration. Typically a drug library contains a list of medications at predefined or standard concentrations, which in turn effectively determines safe dosing ranges. To program such a smart pump with a drug library, the practitioner would typically need to select the particular medication and concentration, enter the patient's weight, program the required infusion parameters such as dose and time, and then enter a command to start the infusion. These steps result in a more complicated workflow for practitioners.

Perhaps a larger challenge to smart pump workflows, however, is in preparing and setting running parameters, etc., before actual use of a pump with a patient. A clinical staff member such as a pharmacist would most likely need to develop a drug library with hard and soft limits for each medication and possibly for each drug concentration as well. In some cases these drug libraries or lists may exceed thousands of entries that need to be defined and entered prior to patient infusions. Developing and maintaining a drug library requires the management of a large number of drug lists, a large amount of hand-entered data, and therefore, involves a considerable amount of time. This problem is exacerbated in any transition to or from the traditional drug library storage component as part of a Hospital Information System (HIS).

It would therefore be useful and advantageous to provide medication safety devices and methods which would meet the needs of both a high and a lower functionality in setting limits and in drug libraries, and which could easily transition from a low functionality to create and maintain a more sophisticated drug library if desired.

SUMMARY

Embodiments of the disclosure provide novel and inventive medication safety devices and methods.

In an embodiment, a medication safety device can include a pump and a drug library in communication with the pump. The drug library can have upper hard and soft limits and lower hard and soft limits associated with at least one drug. A graphical user interface can display a bar chart showing upper and lower soft limit bars for the at least one drug. The upper and lower soft limit bars can be grabbed and dragged, in one particular embodiment, on the graphical user interface in touch-screen fashion to new positions associated with new upper and lower soft limits. The graphical user interface and associated hardware and software can be configurable to responsively re-analyze data and compare a particular infusion to the new upper and lower soft limits. Therefore, in a feature and advantage of various embodiments, user-interactive limiting values are implemented on a drug library for a syringe pump. For example, a slidable Lower Soft Limit (LSL), Upper Soft Limit (USL), Lower Hard Limit (LHL), and/or Upper Hard Limit (UHL) can be utilized to group and ungroup data in the drug library data sets to present limits in relation to known prior infusions. Clinicians or review boards can therefore readily examine the effect of the change to the limits on the number of acceptable and unacceptable infusions falling on some aspect of the LSL, USL, LHL, and/or UHL, or the capability index calculated. Embodiments therefore offer a holistic approach to the creation and maintenance of drug libraries.

In an embodiment, a method of creating a drug library comprises receiving a drug list, the drug list including a plurality of listed drug names, one or more delivery concentrations for each of the listed drugs, and one or more dose rates for each of the listed drugs, receiving operational data from at least one infusion pump, the operational data including information related to an infusion by the at least one infusion pump of at least one of the plurality of listed drugs, and integrating the drug list and the operational data. In an embodiment, a medication safety system comprises at least one infusion pump, and an aggregating server operably coupled to the at least one infusion pump, the aggregating server comprising a processor and memory and configured to: receive a drug list, the drug list including a plurality of listed drug names, one or more delivery concentrations for each of the listed drugs, and one or more dose rates for each of the listed drugs, receive operational data from the at least one infusion pump, the operational data including information related to an infusion by the at least one infusion pump of at least one of the plurality of listed drugs, and integrate the drug list and the operational data to create a drug library.

In an embodiment, a method of transitioning an infusion pump comprises operating the infusion pump in a rate-volume-run mode, operating the infusion pump in a data-gathering mode, and operating the infusion pump in a smart-pump mode.

In an embodiment, an infusion pump comprises a pumping mechanism and a processor configured to operate the infusion pump in a rate-volume-run mode, operate the infusion pump in a data-gathering mode, and operate the infusion pump in a smart-pump mode.

In another feature and advantage of various embodiments, capability indices can be applied to drug library data sets to group and ungroup data in the data sets. For example, a change to the process capability index can automatically create a new chart for comparison having new boundaries or potential limits. Clinicians or review boards can therefore readily examine the affect of the change to the process capability index on the number of acceptable and unacceptable infusions falling on some aspect of the LSL, USL, LHL, and/or UHL.

In another feature and advantage of various embodiments, the user interface described herein can be presented on an operably coupled server, on an integrated viewing device, or on a particular pump. For example, an aggregating server can be operably coupled to one or more pumps, as will be described, for data-gathering utilizing one or more “data gathering” pumps. The aggregating server is configured to receive data from the one or more data gathering pumps and collect or aggregate said data for inclusion in drug library data sets. Thereafter, the user interface presenting drug library and limiting bars can be displayed on the aggregating server for limiting or other data set manipulation and analysis. In another example, the server can aggregate the data as described above, but particular limiting or other data set manipulation and analysis can be conducted on an integrated viewing device operably coupled to the aggregating server, such as a computer, tablet, smartphone, PDA, or other suitable device. In another example, the server can aggregate the data as described above, but particular limiting or other data set manipulation and analysis can be conducted on a pump or other medical device operably coupled to the aggregating server. In embodiments, the pump is the data gathering pump that transmitted infusion data to the aggregating server. In other embodiments, an individual pump can function as the aggregating server.

In another feature and advantage of various embodiments, dynamic data management is provided. In an embodiment, the data aggregated and/or presented can be filtered for patient populations, for example, pediatric patients, geriatric patients, high-risk patients, or low-risk patients, etc. Once aggregated, the data can be filtered according to input from the clinician, review board, or other user. For example, the appropriate limiting for pediatric patients can differ greatly from the limiting for adult patients. Therefore, it may be prudent to provide different upper and lower limits for these populations. Likewise, the limiting appropriate for high-risk adult patients can differ greatly from the limiting appropriate for low-risk adult patients. Data can also be filtered by type of drug, as the limiting appropriate for one drug may not be appropriate for another drug (or even for the same drug of a different concentration). Filters can therefore present the appropriate data sets so that informed decisions can be made to ensure the safety of patients being treated on pumps coupled to the system. Moreover, unlike the static reporting of traditional aggregators, wherein a text document is commonly presented via paper or electronically for board or clinician review, once new or changed limiting values are selected, the values can be automatically programmed to operably coupled pumps.

In another feature and advantage of various embodiments, an aggregating server is configured to calculate when a statistically significant number of data points has been obtained by one or more data gathering pumps. According to the understanding of one skilled in the art, a particular sample size is required in order to make inferences about a particular data population from a sample. Therefore, the aggregating server can automatically calculate the statistically significant number of data points required of any particular data population or data set, filtered or unfiltered. In other embodiments, the data manipulation described herein can also be performed on non-statistically significant sets of data.

In another feature and advantage of various embodiments, the aggregating server can be integrated with other statistically integrated tools and strategies for process improvement, such as Continuous Quality Improvement (CQI), Six Sigma, or Lean Processing, as well as any other suitable improvement process. In an embodiment, for example, any infusion outside of a LSL or USL can be logged as a CQI event. A review board, clinician, or other user can then review and adjust limiting based on the collected data and/or logged events to drive better practice. In other embodiments, the recorded CQI event is used to facilitate training of other clinicians or practitioners involved in the operation of the pumps.

The aforementioned aggregation and automated data analysis and manipulation therefore offers embodiments that reduce the amount of time required to establish drug profiles and limits around those profiles. For example, the manipulation of limits or capability indices in the aforementioned examples is much faster than hand-entering a drug, a drug concentration, the patient weight, and hand-calculating limit boundaries. Time and money is therefore saved by hospitals, clinicians, and administrators implementing embodiments of subject matter hereof

In an embodiment, a method of establishing a smart pump through pump mode transition includes initial operation as a “Rate, Volume, Run” pump, intermediate operation as a data gathering pump, and final operation as a smart pump with drug library interaction. In embodiments, a transition plan aids practitioner training on, and implementation of, smart pumps and drug libraries. For example, a health care facility can have simple “Rate, Volume, Run” pumps, but desire to transition to smart pumps. According to embodiments, emulation of “Rate, Volume, Run” pumps by smart pumps enables practitioners in the facility to become accustomed to the physical designs, layouts, displays, user interfaces and input means, and ergonomics, etc., of the smart pumps before attempting to utilize or interact with advanced smart pump functionality.

In addition to emulation of “Rate, Volume, Run” pumps by smart pumps, data gathered can be analyzed to look for care area or practitioner irregularities or departures from best practices. That is, the smart pumps can employ or provide various data comparison schemes to identify beneficial or detrimental trends or practices in delivery of medication to patients. Also, based on a particular total data set within a hospital, an aggregating server can, for example, show practitioners how many different drug programs or profiles are needed to optimize specific patient population dosing ranges. As such, potentially detrimental “overlap” can be minimized or perhaps even eliminated. For example, one program or profile can be optimized for a neonatal intensive care unit and another program or profile can be optimized for an operating room or surgical suite, etc. Furthermore, “scenario analysis” can thus be optimized, allowing the software to recognize that a particular patient does not belong in a profile that may have been erroneously selected.

The above summary is not intended to describe each illustrated embodiment or every implementation of the subject matter hereof The figures and the detailed description that follow more particularly exemplify these embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments may be more completely understood in consideration of the following detailed description of various embodiments in connection with the accompanying figures, in which:

FIG. 1 is a block diagram of a system for the creation and maintenance of a drug library for the safe delivery of medication, according to an embodiment.

FIG. 2 is a block diagram of a system for the creation and maintenance of a drug library for the safe delivery of medication, according to an embodiment.

FIG. 3 is a flow diagram of a method of creating a drug library, according to an embodiment.

FIG. 4 is an illustration of an example of information that can be required when building a drug library, according to an embodiment.

FIG. 5 is an illustration of an example of implementation of a method of building a drug library with upper hard and soft limits, and lower hard and soft limits, according to an embodiment.

FIG. 6 is an illustration of the example of FIG. 5, wherein new lower and upper soft limits have been set, according to an embodiment.

FIG. 7 is an illustration of the example of FIG. 4, additionally showing compliance for each drug in the library, according to an embodiment.

FIG. 8 is an illustration of an example of a timeline of infusions for a particular patient for evaluation of compliance with the drug library, according to an embodiment.

FIG. 9 is a flow diagram of a method of pump transition, according to an embodiment.

FIG. 10 is a flow diagram of a system for the creation and maintenance of a drug library, according to an embodiment.

While embodiments are amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to be limited to or by the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the subject matter hereof as defined by the appended claims.

DETAILED DESCRIPTION OF THE DRAWINGS

Devices and methods described in greater detail by way of examples herein provide for the scaling and building of drug libraries and medication safety software by way of graphical user interfaces. The devices and methods also provide valuable information on infusions performed in compliance with medication safety parameters, along with automatic or manual updating of drug libraries and a capability of selecting a particular drug in the library and viewing its delivery history and compliance data. The devices and methods further provide for the intuitive and relatively easy transitions from use of basic infusion pumps to smart pump functions. These features and functions are described by example in the following descriptions, with reference to the drawings.

Referring to FIG. 1, a system 100 for the creation and maintenance of a drug library for the safe delivery of medication generally comprises aggregating server 102 and one or more pumps 104 operably coupled to aggregating server 102. In an embodiment, aggregating server 102 comprises one or more drug lists 106, an aggregator 108, and a user interface 110. According to an embodiment of aggregating server 102, a drug list 106 comprises a particular drug name, one or more delivery concentrations, and one or more dose rates for a particular drug. In embodiments, one or more drug lists 106 can comprise a separate list for each unique drug, or a concatenated list for all drugs.

Aggregator 108, in an embodiment, comprises an interface for one or more pumps 104 and storage for data received from the one or more pumps 104. In embodiments, aggregator 108 is configured to receive infusion data from pumps 104. Infusion data can comprise any data related to the infusion(s) performed by the transmitting pump. Referring to FIG. 4, examples of infusion data include the drug name, the pump location, the medication amount, the medication units, the diluent amount, the diluent units, the medication maximum rate, the dose rate dosing unit, dose timing, and limiting data. Infusion data can further comprise other general data about the patient with respect to the infusion, such as patient weight, patient age, patient gender, or other patient characteristics, such as patient risk characteristics. Aggregator 108 is further configured to store the infusion data, either in raw form or a synthesized form, for example, in the coupled storage of aggregating server 102, as will be discussed in reference to FIG. 2.

Generally, as will be discussed in further detail below, one or more pumps 104 send infusion data to aggregating server 102. In particular, aggregator 108 acts as a receiver for the transmitted infusion data. Aggregator 108 then interfaces with drug list 106 to combine or otherwise synthesize the particular drug list with the transmitted infusion data, where applicable. For example, the drug list 106 for HEParin will be integrated by aggregator 108 with transmitted infusion data related to HEParin. This data can then be interfaced to user interface 110 for further manipulation or analysis by a user of aggregating server 102. In general, as will be referred to herein, the combination of a drug list 106 and data from one or more pumps 104 creates a “drug library.”

User interface 110 generally comprises a graphical user interface or other appropriate electronic display for viewing, analyzing, and modifying the synthesized drug library. For example, user interface 110 can be viewable on a computer monitor operably coupled to aggregating server 102. In embodiments, user interface 110 can be integrated into a tablet, smartphone, PDA, or other suitable device. Examples of user interactions with user interface 110 are discussed herein.

Pumps 104 each comprise, for example, a syringe pump to controllably force fluid outwardly therefrom to a patient. Further, an embodiment of pump 104 can comprise a processor and memory, while another embodiment of pump 104 can be in communication with another device which provides such processor and memory functions for interaction of pump 104 with aggregating server 102. In embodiments, pumps are used to control delivery to a patient of medications or fluids that include, but are not limited to: therapeutic agents; nutrients; drugs; medicaments such as antibiotics, blood clotting agents, and analgesics; and other fluids. The devices can be used to introduce the medications or fluids into the body of a patient utilizing any of several routes such as, for example, intravenously, subcutaneously, arterially, or epidurally. Each of pumps 104 comprises a communication interface to aggregating server 102. The communication interface can comprise any number of suitable protocols, and can be wired or wireless, in embodiments. Each of pumps 104 can interface directly to aggregator 108, other components of aggregating server 102.

Referring to FIG. 2, the one or more drug lists 106, aggregator 108, and user interface 110 can be implemented via aggregating server 102 as shown with processor 112, memory 114, and bus 116 in system 200.

Processor 112 can be any programmable device that accepts digital data as input, is configured to process the input according to instructions or algorithms, and provides results as outputs. In an embodiment, processor 112 can be a central processing unit (CPU) configured to carry out the instructions of a computer program. Processor 112 is therefore configured to perform basic arithmetical, logical, and input/output operations.

Memory 114 can comprise volatile or non-volatile memory as required by the coupled processor 112 to not only provide space to execute the instructions or algorithms, but to provide the space to store the instructions themselves. In embodiments, volatile memory can include random access memory (RAM), dynamic random access memory (DRAM), or static random access memory (SRAM), for example. In embodiments, non-volatile memory can include read-only memory, flash memory, ferroelectric RAM, hard disk, floppy disk, magnetic tape, or optical disc storage, for example. The foregoing lists in no way limit the type of memory that can be used, as these embodiments are given only by way of example and are not intended to limit the scope of the subject matter hereof.

Bus 116 comprises one or more subsystems for data transfer between processor 112 and memory 114. As such, bus 116, in an embodiment, is operably coupled to processor 112 and memory 114.

Moreover, referring again to FIG. 2, system 200 is further illustrated with Hospital Information System (HIS) 118 and interfacing device 120.

HIS 118 comprises the information or management system of a hospital, with all of its subcomponents and subsystems. HIS 118 can be configured to transmit data to aggregating server 102 for integration, by aggregator 108, into the drug libraries. Likewise, data can be transmitted from aggregating server 102 to HIS 118 for informational, reporting, or patient care purposes. Such data can be any kind of infusion or patient data as described above.

As shown in FIG. 2, interfacing device 120 is a laptop computer, but can also include a tablet, smartphone, PDA, or other suitable device as discussed above with respect to the integration of user interface 110.

As shown, HIS 118 and interfacing device 120 are operably coupled to aggregating server 102. Such coupling can be implemented by any suitable network protocol, including cellular-type networks such as GSM network protocols, UMTS network protocols, CDMA network protocols and the like or other wireless network protocols such IEEE 802.11 or Wi-Fi, IEEE 802.16 or WiMAX and the like. In embodiments, the coupling is via wired networks, such as Ethernet standards IEEE 802.3. In embodiments, interfacing device 120 can be utilized to build and manage a drug library by access of and interface with the aggregation and synthesizing of aggregator 108 and drug lists 106, in combination with input from HIS 118, where applicable.

Although not illustrated, in another embodiment, HIS 118 can comprise a plurality of HIS platforms or “data warehouses” that contain patient treatment information, etc. Additionally, various treatment and dosing schemes can be advantageously employed through gathering, selecting, and characterizing such patient data as described in, for example, U.S. Pat. No. 6,132,416 and U.S. Patent Application Pub. Nos. 2006/0000480, 2006/0137696, 2010/0057488, and 2011/0264462, each of which is incorporated herein by reference in its entirety.

In embodiments, referring to FIG. 3, a method of building a drug library 300 is illustrated. At 302, a drug list is received; for example, drug list 106. In embodiments, drug list 106 can be provded by, for example, HIS 118 or interfacing device 120, or user interface 110. In embodiments, drug list 106 can be hand-entered or batch downloaded. At 304, aggregating server 102 receives infusion and/or operational data from one or more pumps 104. In embodiments, aggregator 108 receives the infusion and/or operational data. The data can be stored in memory 114 by operation of processor 112 and bus 116. At 306, aggregator 108, in combination with drug lists 106, as described, aggregates and synthesizes the drug lists and received infusion data from pumps 104. As such, a drug library is created. The drug library can then be stored in memory 114 by operation of processor 112 and bus 116, or can be dynamically created by future synthesis of aggregator 108. The drug library can then be implemented on any pumps 104 or other medical devices utilizing similar data. In embodiments, the data gathering of pumps 104 and the implementation of the drug library are on the same pumps. In other embodiments, the data gathering of pumps 104 and the implementation of the drug library are on different pumps.

FIG. 4 illustrates an example of some information that can be used in building a drug library, including LHLs, LSLs, USLs, UHLs. Building a drug library often requires substantial research and data entry time prior to implementation of a pump utilizing such safety information. In contrast, a simple drug list, as mentioned above; for example, drug list 106 can contain relatively less information such as drug names, concentrations, and dose rates, according to an embodiment. For example, a drug list, when combined with a pump that is configured to be a “data gathering” pump, allows clinical personnel to build drug libraries based on current practices.

FIG. 5 illustrates an example of implementation of a method of building a drug library with upper hard and soft limits, and lower hard and soft limits, by way of a graphical user interface or other applicable electronic display and input device (collectively, as referenced throughout this document, “GUI”), such as user interface 110. In a right side inset in FIG. 5, an example of a GUI screen-shot bar chart titled “Dose History for HEParin” is shown. Referring to dashed vertical lines in leftmost and rightmost portions of this bar chart, it is visually apparent that the charted infusions are within the set LSL and USL. In an event that a practitioner would desire to further restrict administration of this drug, the LSL and USL bars could, for example, be “grabbed” and “dragged” on the GUI in touch-screen fashion to such new positions on the GUI as shown in FIG. 6, according to an embodiment. Examples of touch screen devices generally are disclosed in U.S. Patent Application Pub. Nos. 2006/0097991 titled “Multipoint Touchscreen” and in 2011/0193788 titled “Graphical Objects that Respond to Touch or Motion Input,” which are incorporated herein by reference in their entireties. Examples of novel and inventive infusion pump technologies employing touch screen devices are disclosed in U.S. Pat. No. 5,485,408 titled “Pump Simulation Apparatus” and in U.S. Patent Application Pub. No. 2009/0270810 titled “Security Features for a Medical Infusion Pump,” which are incorporated herein by reference in their entireties. In other embodiments, other graphical user interface or non-graphical user interface implementations for updating upper hard and soft limits and lower hard and soft limits are considered, such as through the use of slider bars, text boxes, radio buttons, keyed entry, or any other suitable interface embodiments.

The GUI and its associated hardware and software, for example, referring to FIGS. 1-2 and aggregating server 102 and pumps 104, in embodiments, can then be configured and provided to responsively re-analyze the data, and display on the chart how the infusions charted in FIG. 5 would have compared to the new LSL and USL as charted in FIG. 6. In this example, the new LSL would result in 99.67% compliance and the new USL would result in 96.84% compliance, with a total of 3.49% of all HEParin infusions falling outside the soft limits based on these settings. Upon completion of the analysis the new soft limits can be automatically or manually input to the drug library and uploaded to associated infusion pumps via, for example, a wired or wireless connection as operably coupled as discussed above. It is to be particularly appreciated and understood that adjusting infusion limits in such a manner results in a relatively fast and intuitive representation of the infusion data. This in turn allows a drug library administrator to quickly and easily analyze and change limits based on current best or desired practices.

Additionally, a compliance target can be assigned as a default, in an embodiment. For example, when building the drug library, the default value for compliance could be set to 98%. Based on this default value, the LSL and USL is suggested by the software.

Further, with reference to FIG. 7, compliance of the drug library can be intuitively displayed as shown in the rightmost column of the chart, with compliance being listed for each drug in the drug library. In embodiments, the compliance value or compliance percentage can be highlighted in red, green, or any other color or highlighting scheme to indicate the relative conformity to the particular USL and LSL. For example, a compliance value of 98.2% can be colored green, while a compliance value of 85.0% can be colored red, in order to better highlight to the user the compliance of each particular drug in the drug library. As such, for example, a summary of drug settings would be provided along with compliance data for particular infusions as compared to the settings. For further details, a user could “click on,” “touch on,” or otherwise select a particular drug in the library, with delivery history and compliance data for that particular drug (such as shown, for example, in FIG. 6) then being responsively communicated to and displayed on the GUI.

Referring to FIG. 7, information on basic or simple “Rate, Volume, Run” infusions as aforementioned can also be contained within the drug library (for example, in the bottom row of FIG. 7). In embodiments, the bottom row can be highlighted with coloring or other markings to indicate “Rate, Volume, Run” infusions from infusions utilizing limits and/or compliance with a drug library. The goal of a health care facility using such a medication safety device and method may be 100% compliance (i.e., zero basic infusions) for ensuring patient safety. By having both compliance and non-compliance (i.e., basic) infusion data presented together, practitioners and drug library administrators can effectively and easily monitor overall compliance with infusion safety limits.

Referring now to FIG. 8, an example of a GUI timeline of infusions for a particular patient, for evaluation of compliance with the drug library is illustrated. In some cases, such as in emergency or time-critical situations, practitioners must deliver medications outside normal or otherwise acceptable parameters—such as when, for example, a patient is in imminent danger without administration of a particular life-saving medication. In such situations, practitioners typically will resort to administration of basic “Rate, Volume, Run” infusions or even rapid, manual injections of bolus doses. As shown in the example of FIG. 8, the GUI can display such events as a “pump history” log, thereby increasing awareness of potential occurrences of non-compliance with drug library safety limits. In embodiments, “Rate, Volume, Run” infusions can be highlighted in red, green, or any other color or highlighting scheme to easily allow the user to differentiate those infusions from infusions utilizing limits and/or compliance with a drug library. In this example, pump events are plotted on a timeline: a HEParin infusion was started at 8:17 on Dec. 13, 2011; at 11:38 the same pump was started in a basic infusion mode; at 14:21 it was changed back to a HEParin infusion; and at 18:50 the rate was adjusted to 700 units/hr.

Regardless of a particular embodiment of subject matter hereof, it is to be particularly appreciated and understood that medication safety devices and methods—which have been described by example or otherwise contemplated herein—provide data visualization tools that are easy to use and that facilitate scaling and building of medication safety software and drug libraries, etc. It is also to be particularly appreciated and understood that such information can be efficiently and easily derived from current clinical practice data as aforedescribed.

In an embodiment, medication safety devices and methods can be configured to provide an intuitive transition from “Rate, Volume, Run” pumps to smart pumps. The configuration of the pump, whether a simple “Rate, Volume, Run” pump, data gathering pump, or smart pump, could be controlled by a health care facility to enhance patient protection while making administration of drug libraries and safety limits easier and more efficient.

For example, referring to FIG. 9, a method of pump transition 400 comprises initial operation as a “Rate, Volume, Run” pump 402, an intermediate operation as a data gathering pump 404, and final operation as a smart pump 406 with drug library interaction.

In some instances, a transition plan can be of assistance for practitioner training on, and implementation of, smart pumps and drug libraries. For example, a health care facility can have simple “Rate, Volume, Run” pumps, but desire to transition to smart pumps. Referring to operation as a “Rate, Volume, Run” pump 402, embodiments can provide emulation of “Rate, Volume, Run” pumps by smart pumps. Such a feature allows practitioners in the facility to become accustomed to the physical designs, layouts, displays, user interfaces and input means, and ergonomics, etc., of the smart pumps before attempting to utilize or interact with advanced smart pump functionality. After a desired introductory period has elapsed, the health care facility's infusion pump administrator or manager could then, for example, adjust the pumps' operating parameters to require determination and selection of drugs, drug concentrations from drug lists, and patient weights in transition to smarter pump operations—to allow the practitioners to more easily become accustomed to entering and use of such infusion parameters.

For example, such emulation can be in combination with that of a data gathering pump as in data gathering pump 404 operation, wherein data being gathered is used to build the drug library automatically. In data gathering pump 404 operation, according to an embodiment, intermediate steps within data gathering operation are considered. For example, the data gathering pump 404 can first be implemented with a drug list. Subsequently, the data gathering pump 404 can transmit infusion data related to drugs on the drug list to aggregating server 102 for aggregation by aggregator 108.

As a last step in the transition process from “Rate, Volume, Run” pumps to smart pumps 406, upper and lower hard and soft limits could be employed and compliance could be logged and displayed as aforedescribed. In an embodiment, the smart pump 406 with drug library interaction can include utilizing a pump with a drug library downloaded to the pump, for example, on pumps 104, or by interfacing to the drug library stored on memory 114 of aggregating server 102.

It is to be appreciated and understood that, however, a particular facility could choose to implement any desired transition scheme such as, for example, immediately moving from “Rate, Volume, Run” pumps to smart pumps without the intermediate emulation of data gathering pumps; or emulations could be done in any order with any selected individual or groups of functions. Moreover, the particular mode can be selected among any of the operation as a “Rate, Volume, Run” pump 302, intermediate operation as a data gathering pump 304, or final operation as a smart pump 306 with drug library interaction.

Irrespective of a particular embodiment, it is to be appreciated and understood that medication safety devices and methods—as disclosed by example or otherwise contemplated herein—can be characterized in that intuitive visualization is employed for adjusting parameters of a drug library such as soft limits. Furthermore, the devices and methods can be characterized in that a transition from use of a basic infusion pump to a smart pump can be made by practitioners without a large amount of work for the creation of a drug library or without uncertainty or a lack of efficiency that often accompanies implementation of new devices and methods.

Referring to FIG. 10, a flow diagram of a system for the creation and maintenance of a drug library, according to an embodiment of the subject matter hereof is illustrated. For diagram context, in most basic Rate-Volume-Run operation, for example, that of Rate-Volume-Run pump 402 in FIG. 9, a method is provided by steps 502 and 504, where the rate and volume are set at 502, and the pump is run at 504. In this example of embodiments of a Rate-Volume-Run pump 402, at 506a, a check is conducted to determine whether a drug list is enabled, in combination with user workflow, as depicted. In the Rate-Volume-Run operation, a drug list is not enabled, and operation therefore proceeds to the pump being run at 504.

In embodiments of a data gathering pump, for example, that of data gathering pump 404, data can be gathered for aggregation by aggregating server 102 by interaction with aspects of the pump. At 506 a, if a drug list is enabled, a drug name is selected from the drug list at 508 a. Subsequently, that data is transmitted by the pump device to aggregating server 102.

At 506 b, a check is conducted to determine whether a concentration is enabled. If a concentration is not enabled, the operation again proceeds to the pump being run at 504. However, if a concentration is enabled, a drug concentration is selected from the drug list at 508 b. Subsequently, that data is transmitted by the pump device to aggregating server 102.

At 506 c, a check is conducted to determine whether patient parameters are enabled; for example, a weight-based infusion. If operation with patient parameters is not enabled, the operation again proceeds to the pump being run at 504. However, if operation with patient parameters is enabled, a patient weight is entered at 508 c. Subsequently, that data is transmitted by the pump device to aggregating server 102.

At 506 d, a check is conducted to determine whether age-based patient parameters are enabled. If operation with a patient's age is not enabled, the operation again proceeds to the pump being run at 504. However, if operation with a patient's age is enabled, a patient age is entered at 508 d. Subsequently, that data is transmitted by the pump device to aggregating server 102.

At 506 e, a check is conducted to determine whether gender-based patient parameters are enabled. If operation with a patient's gender is not enabled, the operation again proceeds to the pump being run at 504. However, if operation with a patient's gender is enabled, a patient age is entered at 508 e. Subsequently, that data is transmitted by the pump device to aggregating server 102. Data can be transmitted serially to aggregating server 102 immediately after the aforementioned decision points, or in a batch after processing has completed and the pump is running Therefore, embodiments of data gathering pump 404 can comprise any single or combination of the aforementioned checks and data transmissions, as well as any other suitable data gathering.

Referring, in an embodiment, to smart pump 406 operation, aggregating server 102 is configured to compute drug usage, drug usage by concentration, drug dosing, drug dosing with age, and/or drug dosing with age and gender, or any other appropriate drug or patient data synthesis. In an embodiment, the raw or aggregated data can be flowed back to the pumps from aggregating server 102, as illustrated by the internal data line.

In an embodiment, referring to 510, the aggregated data can be displayed and analyzed by aggregating server 102 in combination with user interface 110, as discussed in FIGS. 4-7, to improve the delivery of medication. As described, embodiments include the updating of limits and content of the drug library. At 512, a check can be conducted by aggregating server 102 or by flags on, for example, pumps 104, to determine if updated drug libraries are desired. In an embodiment, drug library updates can then be transmitted to the pumps at 514.

As described above, HIS 118 can be integrated into the data analysis of aggregating server 102, for example, as illustrated in FIG. 10. For example, when transmitting updates at 514 to the pumps 104, HIS 118 can likewise be updated. Similarly, HIS 118 can transmit data to aggregating server 102 for the inclusion of that data in the drug library analysis.

Regardless of particular components or modes of action, it is to be appreciated and understood that medication safety devices and methods—such as have been described by example or otherwise contemplated herein—can advantageously enhance accuracy, and thus safety and efficacy, in drug delivery to patients.

While medication safety devices and methods have been particularly shown and described with reference to the accompanying figures and specification, it should be understood however that other modifications thereto are of course possible; and all of them are intended to be within the true spirit and scope of novel and inventive devices and methods described herein. Thus, configurations and designs of various features can be modified or altered depending upon particular embodiments. For example, sequencing of various method steps described by example or otherwise contemplated herein can be re-ordered as may be desired in a particular embodiment.

Although subject matter hereof has been described in a context of “syringe pumps”, it is to be appreciated and understood that the subject matter may also be applicable to virtually any infusion delivery device such as, for example, so-called “large volume” pumps and “ambulatory” pumps among others.

It is also to be understood that dimensioning and scaling of the drawings herein have been chosen to clearly show details of example embodiments. Thus, in some embodiments it is possible that spacing between, or orientations of, various features might be variable and visually different from those illustrated. In any event, dimensioning and scaling can vary significantly across various embodiments of medication safety devices and methods.

It is also to be understood in general that any suitable alternatives may be employed to provide novel and inventive medication safety devices and methods as described by example or otherwise contemplated herein.

Accordingly, these and other various changes or modifications in form and detail may also be made, without departing from the true spirit and scope of medication safety devices and methods that may be defined by the appended claims.

Persons of ordinary skill in the relevant arts will recognize that the subject matter hereof may comprise fewer features than illustrated in any individual embodiment described above. The embodiments described herein are not meant to be an exhaustive presentation of the ways in which the various features of the subject matter hereof may be combined. Accordingly, the embodiments are not mutually exclusive combinations of features; rather, the subject matter hereof may comprise a combination of different individual features selected from different individual embodiments, as understood by persons of ordinary skill in the art.

Any incorporation by reference of documents above is limited such that no subject matter is incorporated that is contrary to the explicit disclosure herein. Any incorporation by reference of documents above is further limited such that no claims included in the documents are incorporated by reference herein. Any incorporation by reference of documents above is yet further limited such that any definitions provided in the documents are not incorporated by reference herein unless expressly included herein. 

What is claimed is:
 1. A method of creating a drug library, the method comprising: receiving a drug list, the drug list including a plurality of listed drug names, one or more delivery concentrations for each of the listed drugs, and one or more dose rates for each of the listed drugs; receiving operational data from at least one infusion pump, the operational data including information related to an infusion by the at least one infusion pump of at least one of the plurality of listed drugs; and integrating the drug list and the operational data.
 2. The method of creating a drug library of claim 1, wherein the operational data comprises at least one of a rate parameter, a duration parameter, or a volume parameter for the infusion.
 3. The method of creating a drug library of claim 1, wherein the operational data is at least one of a drug name, an infusion pump location, a medication amount, a medication unit, a diluent amount, a diluent unit, a medication maximum rate, a dose rate dosing unit, a dose timing, a limiting amount, a patient weight, a patient age, a patient gender, or a patient risk characteristic.
 4. The method of creating a drug library of claim 1, wherein the drug list is received from at least one of a hospital information system, a computer, or by manual entry.
 5. The method of creating a drug library of claim 1, wherein integrating the drug list and the operational data comprises limiting at least one of the one or more delivery concentrations for one of the listed drugs, one or more dose rates for one of the listed drugs, or a dose amount for one of the listed drugs according to the operational data.
 6. The method of creating a drug library of claim 5, wherein limiting comprises establishing at least one of a lower hard limit, an upper hard limit, a lower soft limit, or an upper soft limit.
 7. A medication safety system comprising: at least one infusion pump; and an aggregating server operably coupled to the at least one infusion pump, the aggregating server comprising a processor and memory and configured to: receive a drug list, the drug list including a plurality of listed drug names, one or more delivery concentrations for each of the listed drugs, and one or more dose rates for each of the listed drugs, receive operational data from the at least one infusion pump, the operational data including information related to an infusion by the at least one infusion pump of at least one of the plurality of listed drugs, and integrate the drug list and the operational data to create a drug library.
 8. The medication safety system of claim 7, further comprising a hospital information system operably coupled to the aggregating server, wherein the drug list is received by the aggregating server from the hospital information system.
 9. The medication safety system of claim 8, further comprising a data network, wherein the hospital information system is operably coupled to the aggregating server via the data network.
 10. The medication safety system of claim 8, wherein the aggregating server is further configured to transmit data to the hospital information system.
 11. The medication safety system of claim 7, further comprising an interfacing device configured to update at least one of the drug list, the operational data, or the drug library.
 12. The medication safety system of claim 11, wherein the interfacing device is further configured to transmit the drug list to the aggregating server.
 13. The medication safety system of claim 11, further comprising a data network, wherein the interfacing device is operably coupled to the aggregating server via the data network.
 14. A method of transitioning an infusion pump, the method comprising: operating the infusion pump in a rate-volume-run mode; operating the infusion pump in a data-gathering mode; and operating the infusion pump in a smart-pump mode.
 15. The method of transitioning an infusion pump of claim 14, wherein operating the infusion pump in a rate-volume-run mode comprises emulating a rate-volume-run pump by receiving a rate, receiving a volume, and operating the infusion pump based on the rate and the volume.
 16. The method of transitioning an infusion pump of claim 14, wherein operating the infusion pump in a data-gathering mode comprises recording one or more operational parameters of the rate-volume-run mode.
 17. The method of transitioning an infusion pump of claim 14, wherein operating the infusion pump in a smart-pump mode comprises operating the infusion pump with a drug library.
 18. The method of transitioning an infusion pump of claim 17, wherein the drug library is at least partially created based on one or more operational parameters recorded in the data-gathering mode.
 19. An infusion pump comprising: a pumping mechanism; and a processor configured to operate the infusion pump in a rate-volume-run mode, operate the infusion pump in a data-gathering mode, and operate the infusion pump in a smart-pump mode. 